Added Feature ParitionLimitedMode IndexOptimize.sql #964
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sure — here's the full translated version including your new part: --- Sometimes database tables are very large, and not all partitions need to be reindexed. In such cases, only the last few partitions that contain data should be reindexed and have their statistics updated. In the latest update, an option has been added that allows the administrator to specify how many of the most recent partitions should be maintained. This can be done simply by providing the following input parameters when calling **IndexOptimize**: `@PartitionLimitedMode = 'Y'` and `@PartitionDataCount INT = <number_of_partitions>`.
mortezasafaee
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes database tables are very large, and not all partitions need to be reindexed. In such cases, only the last few partitions that contain data should be reindexed and have their statistics updated. In the latest update, an option has been added that allows the administrator to specify how many of the most recent partitions should be maintained.
This can be done simply by providing the following input parameters when calling IndexOptimize:
@PartitionLimitedMode = 'Y' and @PartitionDataCount INT = <number_of_partitions>.
This approach reduces reindexing time, avoids rebuilding untouched partitions, and decreases the workload on the server — especially for large, high-volume operational databases.
For large partitioned tables, older partitions are often read-only and do not require frequent index maintenance or stats updates.
Most data modifications occur in the latest partitions; rebuilding only the last N partitions reduces maintenance time, I/O, and locking/blocking.
This approach is particularly useful for OLTP and reporting systems where recent data is accessed more frequently than historical data.
Helps maintain index performance and statistics without impacting server resources unnecessarily.